Compare Page

Completeness of mandatory attributes

Characteristic Name: Completeness of mandatory attributes
Dimension: Completeness
Description: The attributes which are mandatory for a complete representation of a real world entity must contain values and cannot be null .
Granularity: Element
Implementation Type: Rule-based approach
Characteristic Type: Declarative

Verification Metric:

The number of null values reported in a mandatory attribute per thousand records

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines: Scenario:
Specify which attributes are required to maintain a meaningful representation of an entity. 1) A sales order should at least have values for order number, Quantity, Price and Total (Sales order is the record)
Specify the states of an entity where the above identified attributes become mandatory values (1)Order number quantity and total should be available as mandatory by the time order is created whereas price will become mandatory when the order is approved. (States :"Order created" "Order approved") (2) Product is retired and now has a product-last-available-date
Specify the dependencies of entities in operational context to identify the mandatory values (1)Invoice number should exist to create a gate pass
Specify default values where possible (1) Default country is Australia for those who fill the application from Australian IP addresses

Validation Metric:

How mature is the creation and implementation of the DQ rules to handle mandatory values

These are examples of how the characteristic might occur in a database.

Example: Source:
1) Let us consider a Person relation with the attributes Name, Surname, BirthDate,and Email. The relation is shown in Figure 2.2. For the tuples with Id equalto2,3,and 4, the Email value is NULL. Let us suppose that the person represented by tuple 2 has no e-mail: no incompleteness case occurs. If the person represented by tuple 3 has an e-mail, but its value is not known then tuple 3 presents an incompleteness. Finally, if it is not known whether the person represented by tuple 4 has an e-mail or not, incompleteness may not be the case.

ID 1

2 3 4

Name John

Edward Anthony Marianne

Surname Smith

Monroe White Collins

BirthDate 03/17/1974 02/03/1967 01/01/1936 11/20/1955

Email

smith@abc.it NULL NULL NULL

not existing existing but unknown not known if existing

Fig. 2.2. The Person relation, with different null value meanings for the e-mail attribute

2) if Dept is a relation representing the employees of a given department, and one specific employee of the department is not represented as a tuple of Dept, then the tuple corresponding to the missing employee is in ref(Dept),and ref(Dept) differs from Dept in exactly that tuple.

C. Batini and M, Scannapieco, “Data Quality: Concepts, Methodologies, and Techniques”, Springer, 2006.
if a column should contain at least one occurrence of all 50 states, but the column contains only 43 states, then the population is incomplete. Y. Lee, et al., “Journey to Data Quality”, Massachusetts Institute of Technology, 2006.
1) A database contains information on repairs done to capital equipment. How- ever, it is a known fact that sometimes the repairs are done and the information about the repair is just not entered into the database. This is the result of lack of concern on the part of the repair people and a lack of enforcement on the part of their supervisors. It is estimated that the amount of missing information is about 5%. This database is probably a good-quality database for assessing the general health of capital equipment. Equipment that required a great deal of expense to maintain can be identified from the data. Unless the missing data is disproportionately skewed, the records are usable for all ordinary decisions. However, trying to use it as a base for evaluating information makes it a low-quality database. The missing transactions could easily tag an important piece of equipment as satisfying a warranty when in fact it does not.

2) a BIRTH_DATE value left blank would not be accurate because all of us have birth dates.

J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition: Source:
Domain Level: Data element is 1. Always required be populating and not defaulting; or 2. Required based on the condition of another data element. Entity Level: The required domains that comprise an entity exist and are not defaulted in aggregate. B. BYRNE, J. K., D. MCCARTY, G. SAUTER, H. SMITH, P WORCESTER 2008. The information perspective of SOA design Part 6:The value of applying the data quality analysis pattern in SOA. IBM corporation.
A given data element (fact) has a full value stored for all records that should have a value. ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing.
Determined the extent to which data is not missing. For example, an order is not complete without a price and quantity. G. GATLING, C. B., R. CHAMPLIN, H. STEFANI, G. WEIGEL 2007. Enterprise Information Management with SAP, Boston, Galileo Press Inc.
Completeness refers to the expectation that certain attributes are expected to have assigned values in a data set. Completeness rules can be assigned to a data set in three levels of constraints: 1. Mandatory attributes that require a value 3. Inapplicable attributes (such as maiden name for a single male), which may not have a value.2. Optional attributes, which may have a value. LOSHIN, D. 2001. Enterprise knowledge management: The data quality approach, Morgan Kaufmann Pub.
An expectation of completeness indicates that certain attributes should be assigned values in a data set. Completeness rules can be assigned to a data set in three levels of constraints:1. Mandatory attributes that require a value, 2. Optional attributes, which may have a value based on some set of conditions, and 3. Inapplicable attributes, (such as maiden name for a single male), which may not have a value. LOSHIN, D. 2006. Monitoring Data quality Performance using Data Quality Metrics. Informatica Corporation.

 

Business rules compliance

Characteristic Name: Business rules compliance
Dimension: Validity
Description: Data should comply with business rules
Granularity: Element
Implementation Type: Rule-based approach
Characteristic Type: Declarative

Verification Metric:

The number of tasks failed or under performed due to lack of data precision
The number of complaints received due to lack of data precision

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines: Scenario:
Identify data related business rules separately (business rules that determines the value of data elements and business rules that get executed depending on the values of data elements) and organise them into a separate executable data rules engine (1) The system maintains price routines to handle price related data Element :Discount rate
A price routine (procedure) can be maintained to calculate the discount rate considering the rules

R1:All registered customers get a discount of 6%
R2:All gold customers get a discount of 12%
R3:All purchases greater than $500 get a discount of 5%

Implement a stewardship structure for business rules (parallel to stewardship structure for data) and manage the changes to the rules properly (1) Sales director is responsible for discounts and his approval is needed to change a discount rate. Only the sales manager can change the rules related to discounts.
Maintain an error log to identify the problems resulted in the data rules repository where the problematic data records can be identified precisely (1) Rules engines
Continuously monitor the root causes for the errors recorded in the log and take preventive actions by amending the rules, fixing the technical defects in the system etc. (1) Some trip data is missing for a particular journey in the go card system and as a result an unacceptable journey duration was resulted. New rules were implemented to process such data using a different criteria

Validation Metric:

How mature is the creation and implementation of the data related business rules

These are examples of how the characteristic might occur in a database.

Example: Source:
One common example in education is the student school of record. While most students do not change schools during an academic year, many do, especially in urban settings. Thus, the school at which students are tested may not be the school at which they received most of their instruction. Because school-level student achievement measures become increasingly invalid as the number of mobile students increases, many districts will hold schools accountable only for those students who were enrolled for a full academic year. In this case, student achievement measures for a given school lose validity as the percentage of mobile students increases. J. G. Watson, S. B. Kraemer, and C. A. Thorn, “Data Quality Essentials. Guide to Implementation: Resources for Applied Practice”, August 2009.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition: Source:
Determines the extent to which data is not missing important relationship linkages. For example, the launch date for a new product must be valid and must be the first week of any quarter, since all new products are launched in the first week of each quarter. D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008.
1) Data values conform to the Specified Business Rules.

2) A derived or calculated data value is Produced Correctly according to a specified Calculation Formula or set of Derivation Rules.

ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing.